- Coverage
- 92.86%
26 out of 28 items documented3 out of 28 items with examples - Links
- Homepage
-
actix/actix-web
21542 1666 158 - crates.io
- Dependencies
-
- actix-codec ^0.5 normal
- actix-http ^3.7 normal
- actix-http-test ^3 normal
- actix-rt ^2.1 normal
- actix-service ^2 normal
- actix-utils ^3 normal
- actix-web ^4.6 normal
- awc ^3.5 normal
- futures-core ^0.3.17 normal
- futures-util ^0.3.17 normal
- log ^0.4 normal
- serde ^1 normal
- serde_json ^1 normal
- serde_urlencoded ^0.7 normal
- openssl ^0.10.55 normal optional
- rustls ^0.20 normal optional
- rustls ^0.21 normal optional
- rustls ^0.22 normal optional
- rustls ^0.23 normal optional
- tokio ^1.24.2 normal
- Versions
- Owners
-
Integration testing tools for Actix Web applications.
The main integration testing tool is [`TestServer`]. It spawns a real HTTP server on an
unused port and provides methods that use a real HTTP client. Therefore, it is much closer to
real-world cases than using `init_service`, which skips HTTP encoding and decoding.
# Examples
```
use actix_web::{get, web, test, App, HttpResponse, Error, Responder};
#[get("/")]
async fn my_handler() -> Result {
Ok(HttpResponse::Ok())
}
#[actix_rt::test]
async fn test_example() {
let srv = actix_test::start(||
App::new().service(my_handler)
);
let req = srv.get("/");
let res = req.send().await.unwrap();
assert!(res.status().is_success());
}
```